Configuration-free alert monitoring

ABSTRACT

Systems and methods for generating an event-based data set using a computer implemented asset monitoring system are provided. An asset repository stores data related to one or more commissioned assets of an asset monitoring system. When event data is received from an asset, whether an asset maintenance record corresponding to the asset exists in the asset repository is determined based on comparing the data in the asset repository to the event data. When the asset maintenance record is determined to not exist in the asset repository, an asset identification record corresponding to the asset is rendered. The asset identification record comprises the event data and additional asset-related data collected from the asset. An event-based data set is generated based on the asset identification record.

BACKGROUND

Maintenance operations related to system assets are assisted through theuse of maintenance software applications. The applications typicallymonitor asset health for a broad range of system assets, such as assetsused in process control, assets that implement home or commercialsecurity, assets related to commercial vehicles, or assets that provideaccess control based on security privileges of various personnel. Theapplications typically function in coordination with various platforms,such as industrial process control platforms used to implement a controlstrategy on field devices or other production line components.Maintenance applications of this type typically enable personnel taskedwith asset management, such as maintenance supervisors, to viewasset-related information and to determine as well as execute amaintenance plan based on the viewed information.

These types of maintenance applications typically require configuringthe application by organizing information related to managed assets asstructured data, capable of being presented to the application and beingdisplayed to maintenance personnel as a hierarchical tree of systemassets. Configuration is typically required in order to properly enablethe application to effectively monitor the maintenance status ofthousands of assets. Unfortunately, configuration of this type alsorequires either a strong dependency on a particular system datastructure or significant, replicated work.

Many parts of the system being monitored by the application, notablyintelligent devices like transmitters and valve positioners in the caseof an industrial process control system, are capable of detectingirregular or noteworthy conditions and reporting these conditions to theplatform as “events”. Unfortunately, current maintenance softwareapplications are not capable of interacting with assets that have notbeen conventionally configured. Furthermore, current maintenancesoftware applications require conventional configuration in order tointerpret “event data” received from assets, such as asset-specificconditions reported to the maintenance software as alarms, or alerts. Asa necessary consequence, current maintenance software applications alsorequire configuration in order to provide asset documentation services,such as historical records of conditions or reports detailing currentconditions associated with an asset.

SUMMARY

Aspects of the present invention permit a maintenance application tointeract with assets without previously configuring an asset, by relyingon event data such as asset-specific conditions reported as alarms oralerts by intelligent devices. Moreover, aspects of the invention permitthe receiving of event data, and the generation of event-based data setscomprising unique data used by maintenance applications, in order toproperly manage the assets that are monitored. By providing amaintenance software application that accesses stored asset-related databased on received event data without requiring an asset to beconfigured, the present invention provides for a historical record ofmaintenance-related data to be constructed from a “configuration-free”asset, and for asset documentation services to be provided withoutreliance upon a particular system data structure and without requiringsignificant, replicated work for configuration personnel.

In an aspect, a computer implemented asset monitoring system isconfigured to generate an event-based data set. The system includes anasset repository storing data related to one or more commissioned assetsof an asset monitoring system. The system also includes aprocessor-readable memory storing processor-executable instructionsthat, when executed, generate an event-based data set. The instructionsreceive event data from an asset and determine, based upon comparing theasset-related data in the asset repository to the received event data,whether an asset maintenance record corresponding to the asset exists inthe asset repository. The instructions further render an assetidentification record corresponding to the asset where the assetmaintenance record is determined to not exist in the asset repository.The asset identification record comprises the event-based data set andfurther comprises additional asset-related data collected from theasset. Additionally, the instructions generate the event-based data setbased on the asset identification record.

In another aspect, a tangible processor-readable memory storingprocessor-executable instructions for generating an event-based dataset.

In yet another aspect, a computerized method for operating an assetmonitoring system to generate an event-based data set is provided.

Other objects and features will be in part apparent and in part pointedout hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a system configured to generate an event-based data setin an asset monitoring system according to an embodiment of the presentinvention.

FIG. 2 depicts functional relations among and tasks completed by varioussoftware components that interact to provide the event-based data setgeneration system depicted in FIG. 1 according to an embodiment of thepresent invention.

FIG. 3 depicts the generation of an event-based data set according to anembodiment of the present invention.

FIG. 4 depicts a computerized method for generating an event-based dataset according to an embodiment of the present invention.

FIG. 5 depicts generating updated determinations related to event-baseddata set generation according to an embodiment of the present invention.

FIG. 6 is an exemplary screen shot depicting a user interface fordisplaying various details based on data capable of being derived fromreceived event data according to an embodiment of the present invention.

FIG. 7 is an exemplary screen shot of contextualized alerts derived froman event-based data set according to an embodiment of the presentinvention.

FIG. 8 is an exemplary screen shot of a user interface for displayingdetailed alert data related to received event data according to anembodiment of the present invention.

Corresponding reference characters indicate corresponding partsthroughout the drawings.

DETAILED DESCRIPTION

FIG. 1 depicts one example of an asset maintenance system configured toreceive updates related to assets that comprise the system. In anembodiment, the asset maintenance system comprises an industrial processcontrol system 100 configured to provide supervisory level and/orregulatory level control of an industrial process. In the course ofexecuting process control, the system 100 monitors, logs, and displaysrelevant manufacturing/production events and associated data. Inaddition, the system 100 is configured to generate an event-based dataset according to an embodiment of the present invention. The system 100comprises an asset repository 109 (e.g., a persistent store, such as adatabase) storing asset-related data. The asset-related data isaccessible by the system 100 based in part upon event data received bycomponents of the system 100 as will be described herein. In anembodiment, the asset-related data comprises asset-specific data that isused by interpreting an asset parameter descriptive of the condition ofan asset 112. The asset repository 109 is configured to storeasset-related data comprising an event-based data set descriptive of anasset maintenance record. In an embodiment, the asset 112 is a fielddevice, such as a valve positioner or a transmitter, under the controlof the process control system 100 and the asset parameter furthercomprises a diagnostic bit set. Additionally or alternatively, otherexamples of asset maintenance systems include various process controlsystems, such as control systems used to automate the power electronicsand associated components used in elevator control systems. Additionalexamples of asset maintenance systems further comprise: assets used inthe implementation of security alarm systems, assets used in themonitoring of vehicle fleets such as commercial vehicle fleets, andassets used to restrict and/or monitor access based on personnelcategory (e.g. employee, visitor, general public, etc.) and/or otherfactors, through the use of assets such as access badges, identificationcards, or the like.

Aspects of this invention relate to a system for generating anevent-based data set by accessing asset-related data in the assetrepository based upon received event data (e.g., an asset parameter)received from an asset, such as an intelligent field device. In anembodiment, the asset parameter comprises a diagnostic bit set.Additionally or alternatively, the asset parameter comprises a parameterprovided by an asset, such as a parameter descriptive of currentamplitude applied to a valve positioner, and/or various forms of dataprovided by assets used in the asset maintenance systems describedabove. In another embodiment, the asset parameter is collected from theasset by a diagnostic contextualization component 115. In yet anotherembodiment, the asset parameter is based upon various forms ofobservational data related to an asset such as video, or based upon datadescriptive of the video such as text-based data files.

In an embodiment, diagnostic contextualization component 115 isconfigured to retrieve sufficient relevant data based on the bit set.The diagnostic contextualization component 115 is configured to receivealerts from controllers 118 and to prioritize data related to alertsusing asset alarm triage component 121. A service interface 124communicates with diagnostic contextualization component 115 to accessasset repository 109 based on event data received from assets 112. Theservice interface 124 is configured to connect to asset condition datasuch as alerts, as well as to check incoming condition data againstasset repository 109 to identify historical information related to theasset, providing asset identification and maintenance without requiringconfiguration of the asset 112 beforehand. In this manner, the systemutilizes service interface 124 to connect to asset condition data andallow any asset or system to deliver conditions, asset metadata,maintenance instructions, updates, and the like to the asset repository109.

The first steps in the use of a conventional asset managementapplication are typically configuration activities. These activitiesusually consist of creating templates to define asset types or classes,creating instances of those types of assets, configuring the parametersof the assets and deploying those parameters to the assets in a stepcalled commissioning. Configuration is required to make the assetsoperate correctly and generally cannot be avoided. Asset managementapplications that are used in the systempost-configuration/commissioning (e.g., maintenance took) typicallypresent a hierarchical (tree) view of the system assets being managed.Assets are located by browsing, or searching the asset hierarchy.Usually, these downstream tools consume the data from the configurationtool's database or require their own manual configuration. This eitherestablishes a strong dependency on a particular system data structure ormeans significant, replicated work for configuration. Aspects of thepresenting invention advantageously interact with assets 112 having noprevious asset configuration. By providing configuration-free assetmaintenance as described herein, significant improvements to assetmaintenance efficiency are possible: asset condition history is moreeasily documented, major events (such as asset hardware replacement) areautomatically captured without requiring manual reconfiguration, andintermediaries (e.g., system platform software, stand-alone conditionmonitoring applications, etc.) can be used to transformprotocol-specific conditions into a usable format.

In an embodiment, diagnostic contextualization component 115 is furtherconfigured to generate a contextualized alert based on the retrieveddata after retrieving the relevant data. The contextualized alertincludes asset-related data such as alert (i.e., “condition”) details,system context, asset-specific documentation data, and historicalinformation about previous maintenance. The diagnostic contextualizationcomponent 115 also generates an alert resolution status in part basedon, for example, determining whether data related to an actionableoutput (i.e., planned asset maintenance) exists for the asset 112. Thealert resolution status comprises data that allows for thecontextualized alert to be presented as a prioritized list, such as alist displayed to a maintenance supervisor as part of a dashboard, forexample.

In an embodiment, the asset 112 comprises an intelligent field devicecapable of detecting irregular or noteworthy asset-related details thatare of particular interest to maintenance personnel tasked with usingmaintenance tools to maintain aspects of control system 100. In anotherembodiment, the noteworthy asset-related details are of interest tomaintenance personnel, in contrast to plant operation personnel who aretasked with operating the control system 100. In an embodiment, thecomponent 115 is implemented in combination with process control system100 used on a production line.

Still referring to FIG. 1, the asset-specific data stored in the assetrepository 109 further comprises asset identification data and alertprioritization data. In an embodiment, the asset repository 109comprises an asset information directory, an alert historian, and analert profile historian. The diagnostic contextualization component 115is coupled to the asset repository 109 and is configured for generatingan event-based data set. According to aspects of the invention, thesystem of FIG. 1 interacts with events as conditions are presentedrather than a system tree. Each asset 112 is able to deliver conditionsto the system even when the system has never been configured to knowabout the particular asset 112. This makes the system essentiallyconfiguration-free. It can be installed where assets 112 deliverconditions using the interface services and is capable of immediatelygathering conditions and information gathering information about theassets 112 that create them. A historical record of all conditions ismaintained along with the history of work orders executed against them.Reports that detail all current conditions associated with the asset 112and all of its condition and maintenance history are made available. Inan embodiment, the diagnostic contextualization component 115 isconfigured to detect asset-related details related to maintaining theasset in an optimal state of performance, and is configured fordistributing asset-related details to the appropriate maintenance staffand providing various data including asset-related details, systemcontext, and historical information about previous maintenance.

The diagnostic contextualization component 115 is configured forgenerating event-based data by accessing asset-related data in the assetrepository 109 via service interface 124, which is configured toevaluate the asset-related data based on the received event data. Thediagnostic contextualization component 115 is further configured forgenerating an event-based data set based on the accessed asset-relateddata. In an embodiment, the diagnostic contextualization component 115is further configured to generate a contextualized alert based onretrieved asset identification data and retrieved alert prioritizationdata. In this manner, diagnostic contextualization component 115determines whether actionable output related to the contextualized alerthas been received, which permits generating an alert resolution statusbased on the determination. The diagnostic contextualization component115 is configured to perform functions based at least in part upon thegenerated event-based data set.

In an embodiment, the service interface 124 comprises one or moreindustry standard service interfaces, such as Windows CommunicationFoundation (WCF) services interfaces or web services interface or thelike. In another embodiment, the service interface 124 comprises atleast one interface standard used to enable inter-process and/orinter-system communication, such as the component object model (COM),the Common Object Request Broker Architecture (CORBA), Java MessagingService (JMS), and the like. In yet another embodiment, the serviceinterface 124 is configured to allow any asset or system to deliverasset-related data to the asset repository, such as conditions, assetmetadata, and instructions related to updating alert profile data, aswill be described herein.

The event-based data set is configured for providing data that allowsfor the display of information related to an alert, such as datacomprising a contextualized alert status that provides for the displayof alerts in the form of a prioritized list of asset-related detailsordered by severity. In an embodiment, the prioritized list ofasset-related details comprises contextualized alerts generated frominformation accessed in the asset repository 109 by the diagnosticcontextualization component 115. An asset alarm triage component 121functions as part of the diagnostic contextualization component 115 todetermine and generate data related to an alert resolution status. Inturn, diagnostic contextualization component 115 accesses the alertresolution status to present the contextualized alerts as aconsolidated, prioritized list, generating asset-related data thatallows for detected conditions to be presented in a manner that improveshow actionable descriptions are organized and communicated. Datacomprising the prioritized list is configured for display asasset-related details ordered by severity for use with reports anddashboards 117. In an embodiment, the reports and dashboards 117 arepresented on a user interface. Additionally or alternatively, thereports and dashboards 117 are presented as part of a web application.

Still referring to FIG. 1, service interface 124 is configured toreceive event-based data (e.g., an “alert,” an “asset parameter,” or a“diagnostic bit set”) from an asset 112 and to complete tasks related tobuilding an event-based data set related to the asset 112 withoutrequiring the asset 112 to have been previously configured.Configuration of the asset 112 comprises tasks such as creatingtemplates defining an asset type or asset class, or creating instancesof the type of asset 112, and typically requires dependence upon aparticular data structure or significant manual work. In an embodiment,the service interface 124 communicating with the diagnosticcontextualization component 115 receives the alert from the asset 112 bycommunicating with a controller 118 to pass the asset parameter to thediagnostic contextualization component 115 via the service interface 124associated with diagnostic contextualization component 115. The serviceinterface 124 is programmed to provide, for example, configuration-freealert monitoring by providing received alerts as event-based data to thediagnostic contextualization component 115.

With further reference to FIG. 1, in the illustrated embodiment, theservice interface 124 in communication with the diagnosticcontextualization component 115 is configured to receive an assetparameter passed via a multiplexer 127. The asset 112 as shown in FIG. 1also communicates with a safety processor 130. In an embodiment, thesafety processor 130 comprises processors configured to independentlyprocess inputs from one or more assets 112 and the processors “vote” onthe data in part to provide a safety barrier between the data providedby the assets 112 and an application configured to monitor the assets112. The multiplexer 127 communicates with a maintenance data collectioncomponent 133 in the illustrated embodiment to pass the asset parameterfrom the communicating asset 112 to the diagnostic contextualizationcomponent 115. The service interface 124 associated with the diagnosticcontextualization component 115 receives asset parameters from themultiplexer 127. In yet another embodiment, maintenance data collectioncomponent 133 communicates with the multiplexer 127 and the serviceinterface 124 of the diagnostic contextualization component 115 tofacilitate the transmission of asset parameters from assets 112 to thediagnostic contextualization component 115.

Still referring to FIG. 1, in an embodiment, asset-specific dataprovided by the asset repository 109 further comprises alert responsedata. And alert response data further comprises descriptive data thatprovides context related to the state of the asset parameter, as will befurther described herein. In another embodiment, the alert response datafurther comprises: other alerts reported by the particular asset 112;installation history for asset 112; location details related to asset112; and maintenance work planned for asset 112. The diagnosticcontextualization component 115 is preferably configured to generate analert resolution status based upon comparing the alert response data tothe alert resolution status to render actionable output, as will befurther described herein. This actionable output comprises, for example,data describing work planned for asset 112.

The diagnostic contextualization component 115 of FIG. 1 providesupdated data in the form of an alert resolution profile to a resourceplanning system 139. The resource planning system 139 is configured tointerpret and integrate real time data for use with process executionapplication tools. In an embodiment, the diagnostic contextualizationcomponent 115 is further programmed to determine, based upon comparingthe accessed asset-related data to the received event data, whether anasset maintenance record exists in the asset repository 109 andrendering an asset maintenance record where an asset maintenance recordis determined not to exist in the asset repository. In this regard, theasset maintenance record includes an event-based data set as well asadditional asset-related data. The diagnostic contextualizationcomponent 115 is further programmed to combine the accessedasset-related data with the received event data to update the assetmaintenance record where an asset maintenance record is determined toexist in the asset repository. In an embodiment, the diagnosticcontextualization component 115 generates an event-based data setcomprised of data accessed to generate a result related to theactionable output, the alert resolution profile, and the alertresolution status.

In an embodiment, the asset-related data comprises data descriptive ofthe asset 112. The data descriptive of the asset comprises an alertrecord including a historical record of all alerts, and an alertresolution profile record comprising a history of tasks executed inresponse to the alert, that are executed in order to resolve the alert.In another embodiment, the alert resolution profile record is based ondata used to generate an alert resolution profile. In yet anotherembodiment, data used to generate the asset maintenance record comprisesasset identification data, alert prioritization data, and alert responsedata, as will be further described herein.

FIG. 2 depicts functional relations among various software componentsthat interact to provide the event-based data set generation systemdepicted in FIG. 1 according to an embodiment of the present invention.Moreover, FIG. 2 illustrates tasks completed by the components. In anembodiment, the functional relations depicted in FIG. 2 allow forvarious components to complete tasks that result in the installation,control, and monitoring of assets in a manner that increases theeffectiveness of the asset monitoring system, resulting in improvedresults such as increased process control system efficiency. Monitoringthe maintenance status of assets includes, for example, generating data(i.e., the event-based data set) to allow for asset maintenance tasks tobe executed without requiring the establishment of a strong dependencyupon a particular system data structure. In an embodiment,contextualized alerts are generated by accessing data used by thediagnostic contextualization component 115 to generate the event-baseddata set.

Tasks related to engineering and commissioning an asset maintenancesystem configured to monitor an asset, such engineering andcommissioning component 180 configured to monitor and controls asset 112as part of an asset monitoring system strategy are conventionallycompleted using an asset manager such as field device manager softwareor the like. In an embodiment, tasks related to an asset monitoringsystem adjustment component 204, in part based on results generatedbased on an alert profile management component 201, are also typicallycompleted using field device manager software. According to aspects ofthe invention, installation of an asset, such as asset 112, requiresaction by the engineering and commissioning component 180. A measure andcontrol component 183 is configured to complete tasks that result inimplementation of a control system strategy, as well as to adjust thecontrol system in part based on asset parameters that are measured bythe control system during implementation of the control system strategy.Tasks related to the measurement and control of an asset, such as asset112, are completed using distributed control system and safety software,in one embodiment.

As previously described in connection with FIG. 1, the diagnosticcontextualization component 115 is configured for generating anevent-based data set by accessing asset-related data from the assetrepository 109. In an embodiment, the diagnostic contextualizationcomponent 115 is configured to execute various tasks to generate anevent-based data set. In another embodiment, the various tasks arefurther accomplished by components within the diagnosticcontextualization component 115. Runtime monitor 186 component executestasks that allow for an asset parameter transmitted from the asset 112to be monitored in real time. In an embodiment, runtime monitor 186interacts with a measure and control component 183 to execute tasksallowing for data related to measure and control applications as well asruntime monitoring applications to be updated in real time and madeavailable to the diagnostic contextualization component 115 duringevent-based data set generation 207 as shown in FIG. 5. The diagnosticcontextualization component 115 is further configured in an embodimentto provide functionality of a runtime monitor 186.

Diagnostic contextualization component 115 is also configured tocomplete additional tasks and to operate various components that providedata related to event-based data set generation 207. In an embodiment,the diagnostic contextualization component 115 includes an alertcontextualization component 189 that performs contextualization tasksthat provide context to asset parameters. The alert contextualizationcomponent 189 provides, for example, descriptive data related to assetparameters. In operation, tasks executed by the alert contextualization189 component generate data used to uniquely present the full contextneeded to generate an action related to a contextualized alert, and thedata is made available to the diagnostic contextualization component 115during event-based data set generation 207. The service interface 124 inthe illustrated embodiment connected to the diagnostic contextualizationcomponent 115 performs the alert contextualization component 189 tasksand the runtime monitor 186 tasks previously described.

Referring further to FIG. 2, an alert triage component 192 of diagnosticcontextualization component 115 completes alert triage 192 tasks, anduses data generated from alert triage 192 tasks during event-based dataset generation 207. Alert triage component 192 provides contextualizedalerts as a prioritized list, resulting in the generation of a list ofasset-related details ordered by severity. In an embodiment, alerttriage component 192 completes asset alarm triage component 121 tasks,such as determining the alert resolution status as described above. Thediagnostic contextualization component 115 accomplishes alert responsegeneration tasks as indicated at reference character 195 based on tasksperformed by the alert triage 192 and uses data generated from alertresponse generation 195 tasks during event-based data set generation 207to generate an event-based data set 230 (see FIG. 3).

An alert profile generation component 198 generates data related to analert profile for determining whether an actionable output related tothe contextualized alert has been received. Determining whether theactionable output related to the contextualized alert has been receivedincludes rendering data descriptive of the asset parameter that isspecific to the alert resolution profile, such as data used to generatean active alert resolution profile, as will be further described herein.In an embodiment, the alert response generation tasks comprise silencingthe alert as well as alert profile generation 198.

The alert profile management component 201 of the diagnosticcontextualization component 115 is additionally configured to completetasks related to the generated alert profile 198 provided based on thegenerated alert response 195. The diagnostic contextualization component115 is configured to use the data generated from alert responsegeneration 195 tasks, alert profile generation 198 tasks, and alertprofile management 201 during event-based data set generation 207.

In an embodiment, the asset monitoring system adjustment component 204is configured for adding to the knowledge base related to the asset 112,adjusting asset parameters that determine an operating state of theasset 112, implementing repair functions pertaining to the asset 112,and implementing replacement functions related to the asset 112. Thediagnostic contextualization component 115 is also configurable toutilize the data generated from asset monitoring system adjustment 204during event-based data set generation 207 to generate an event-baseddata set.

FIG. 3 depicts the generation of an event-based data set, according toan embodiment of the present invention. The generation of an event-baseddata set 230 by the diagnostic contextualization component 115 isaccomplished during event-based data set generation 207 (see FIG. 2). Inan embodiment, data related to the generation of an event-based data set230 is used by the diagnostic contextualization component 115 togenerate a contextualized alert. An event-based data set 230 isgenerated based in part upon an asset parameter provided from asset 112as previously described. The controller 118 provides the assetparameter, which comprises a diagnostic bit set 236. The asset-relateddata of event-based data set 230 includes asset-specific data 239obtained from the asset repository 109. In an embodiment, theasset-specific data 239 further comprises asset identification data 242when the particular asset 112 has been configured, alert prioritizationdata 245, and alert response data 248.

In an embodiment, the asset identification data 242 provides for themeaning of a diagnostic bit set 236 to be interpreted, for example wheretwo identical diagnostic bit sets 236 received by the diagnosticcontextualization component 115 via two different assets 112 havedifferent meanings based upon the particular asset 112 sending thediagnostic bit set 236. The diagnostic contextualization component 115is configured to interpret the diagnostic bit set 236 based in part uponthe asset 112 transmitting the diagnostic bit set 236 using assetidentification data 242 retrieved from the asset repository 109. Theservice interface 124 connected to the diagnostic contextualizationcomponent 115 interprets the diagnostic bit set 236 to provide access toasset-related data located in the asset repository 109 to generateevent-based data set 230. In an embodiment, event-based data set 230 isgenerated in part based upon the asset identification data 242. Inanother embodiment, asset identification data 242 comprisesasset-specific documentation data useful in interpreting the diagnosticbit set 236.

Additionally or alternatively, event-based data set 230 is generated bydiagnostic contextualization component 115 after diagnosticcontextualization component 115 accesses alert prioritization data 245via service interface 124. In an embodiment, the service interface 124connected to diagnostic contextualization component 115 accesses assetrepository 109 based on asset-specific data 239 comprising alertprioritization data 245. Alert prioritization data 245 provides datarelated to the maintenance history of asset 112 as well as data relatedto the installation history of asset 112. The event-based data set 230is generated by diagnostic contextualization component 115 using thealert prioritization data 245 accessed based on the diagnostic bit set236 provided to the service interface 124. In an embodiment, serviceinterface 124 comprises a WCF service interface, and the WCF serviceinterface further comprises a set of service interfaces configured toparse at least one of the following from the asset-related data:implementation data related to implementing one or more assetmaintenance services natively on an asset 112 such as a field device,wherein the implementation data is independent from application supportdata relating to application services that are external to the fielddevice; and data related to transforming the alert into aprotocol-specific format.

The diagnostic contextualization component 115 is further configurableto accomplish the tasks of alert contextualization component 189 andalert triage component 192 based on the retrieved alert prioritizationdata 245 and the retrieved asset identification data 242 and to use datarelated to accomplishing the tasks to generate event-based data set 230.In another embodiment, diagnostic contextualization component 115retrieves alert prioritization data 245 from the asset repository 109based on the asset identification data 242, and uses data related toretrieving the alert prioritization data 245 in combination with thetasks as described above to generate event-based data set 230.

In an embodiment, diagnostic contextualization component 115 is furtherconfigured to determine whether actionable output related to acontextualized alert has been received. The diagnostic contextualizationcomponent 115 is additionally configured to generate an alert resolutionstatus based on the determination. In an embodiment, actionable outputcomprises data related to whether maintenance work has been planned foran asset. In another embodiment, the alert resolution status comprisesdata that allows for the manipulation of information related to thecontextualized alert by the diagnostic contextualization component 115.The alert resolution status comprises data that allows for alertresponse generation tasks 195 to be accomplished. In an embodiment, thealert resolution status comprises data that allows for contextualizedalerts to be displayed as a prioritized list of asset-related detailsordered by severity. In another embodiment, data related to determiningwhether actionable output related to a contextualized alert has beenreceived is used by the diagnostic contextualization component 115 togenerate event-based data set 230.

FIG. 4 depicts a computerized method for generating an event-based dataset, according to an embodiment of the present invention. The processdepicted by FIG. 4 begins at 281, where an asset repository 109 isprovided. The asset repository 109 is configured for storingasset-related data comprising an event-based data set 230 descriptive ofan asset maintenance record. At 284, asset-related data is provided tothe asset repository 109 via a service interface 124 configured tocollect the asset-related data based on received event data. At 287, anevent-based data set 230 is generated based on the accessedasset-related data. In an embodiment, the process continues at 290,where it is determined whether an asset maintenance record exists in theasset repository 109. If it is determined that an asset maintenancerecord exists in the asset repository 109, the process concludes at 293where the accessed asset-related data is combined with the receivedevent data to update the asset maintenance record. If it is determinedthat an asset maintenance record does not exist in the asset repository109, an asset identification record is rendered comprising anevent-based data set 230 and further comprising additional asset-relateddata.

FIG. 5 depicts generating updated determinations related to event-baseddata set generation, according to an embodiment of the presentinvention. In an embodiment, the diagnostic contextualization component115 is configured to interact with various software components duringevent-based data set generation 207, such as the various componentsdescribed above with reference to FIG. 2. The diagnosticcontextualization component 115 is configured to determine at 339whether an asset maintenance record exists in the asset repository, asdescribed above with reference to FIG. 4. In the event an assetmaintenance record exists in the asset repository 109, the assetmaintenance record is updated. However, if it is determined at 339 thatan asset maintenance record does not exist in the asset repository 109,event-based data set generation 207 continues, and an assetidentification record is rendered comprising an event-based data set 230and further comprising additional asset-related data.

In yet another embodiment, generating an event-based data set 230 duringevent-based data set generation 207 comprises collecting additionalasset-related data from the service interface. Such asset-related datais the type of information usually collected during the commissioningprocess and relates to at least one of: asset vendor data, model data,serial number data, location data, and version data. In other words, thesystem, via service interface 124, checks incoming conditions againstthe repository 109 to determine if a condition has ever been receivedfrom the source asset 112. If no conditions have been receivedpreviously, the service interface 124 collects additional metadata aboutthe reporting asset 112. This metadata includes items like the assetvendor, model, serial number, location, version, etc. In addition,service interface 124 allows major events (e.g., asset hardwarereplacement) to be captured automatically without the need to manuallyre-configure the instance for the changes. Any asset 112 connected tothe system Ethernet network, for example, could be programmed toimplement one or more of the services natively. Alternatively, anintermediary such as Wonderware System Platform available from SchneiderElectric or a stand-alone condition monitor application can be used totransform conditions in a protocol-specific format into the serviceinterface 124.

Referring further to FIG. 5, event data used to generate event-baseddata set 230 comprises an alert descriptive of an asset, such as, forexample, at least one of a transmitter and a valve positioner.Generating the event-based data set 230 further comprises combining theprovided asset-related data with the stored event-based data set togenerate an alert log entry in the asset maintenance record. In anotherembodiment, the alert log entry comprises data describing an updatedstate of the alert when the combined reporting asset input comprisesdata related to a mitigated state of the alert and data associating eachasset with at least one of an active alert related to the asset and analert resolution profile related to the asset.

FIG. 6 is an exemplary screen shot depicting a user interface fordisplaying various details based on data capable of being derived fromreceived event data according to an embodiment of the present invention.In the illustrated embodiment, a dashboard 375 is rendered based on datagenerated by the diagnostic contextualization component 115 as well asdata related to the diagnostic bit set 236 and received by thediagnostic contextualization component 115 via the service interface124. The diagnostic contextualization component 115 is configured togenerate an event-based data set 230 based on asset-related dataaccessed in the asset repository 109 by the service interface 124. In anembodiment, a portion of the data accessed to render the variousdisplays comprising the dashboard 375 is related to the data the serviceinterface 124 accesses in the asset repository 109 when generating theevent-based data set 230 based upon received event data.

In an embodiment, contextualized alerts generated based upon diagnosticbit sets 236 are displayed as a prioritized list of asset-relateddetails ordered by severity. In an embodiment, the prioritized list ispresented as an active alert display 381 comprising a summarizedseverity ordered contextualized alert list 378 on the dashboard 375. Thedata used to generate the summarized alert list 378 is comprised ofsummarized contextualized categories 384 derived from data related tothe contextualized alert and organized as the summarized alert list 378based upon the alert resolution status generated by the diagnosticcontextualization component 115. The summarized contextualizedcategories 384 are comprised of, for example, NAMUR category data, alerttag ID data, alert timestamp data, alert message data, and the like. Inan embodiment, a summarized alert 387 comprises a contextualized alertcapable of being ordered by severity, and is further comprised ofsummarized contextualized categories 384.

Additionally or alternatively, data generated by the diagnosticcontextualization component 115 as well as data related to thediagnostic bit set 236 and received by the diagnostic contextualizationcomponent 115 is used to generate additional displays on the dashboard375 based upon data related to the contextualized alert and prioritizedaccording to the generated alert resolution status. In an embodiment, anadditional display comprises an asset trend priority display 390generated to provide an alternative representation of asset-related dataprioritized according to the generated alert resolution status. Anadditional display comprises an alert area distribution display 393rendered based on data generated by diagnostic contextualizationcomponent 115 including location details related to the asset 112.

Still referring to FIG. 6, in an embodiment, data generated by thediagnostic contextualization component 115 as well as data related tothe diagnostic bit set 236 and received by the diagnosticcontextualization component 115 is used to generate an active alertprofile display 396. The active alert profile display 396 comprises asummarized alert resolution profile list 399. The data used to generatethe summarized profile list 399 is capable of being organized as profilecategories 402 and further comprise, for example, work order numberdata, tag id data, problem description data, and the like. In anembodiment, an active alert resolution profile 405 is comprised ofprofile categories 402. And in an embodiment, the data used to renderthe profile categories 402 is generated by the diagnosticcontextualization component 115 during alert response generation 136 toprovide a result related to actionable output to update the alertresolution profile.

The diagnostic contextualization component 115 is further configured torender data descriptive of the asset parameter that is specific to thealert resolution profile, in order to generate data used for the activealert profile display 396. The diagnostic contextualization component115 is also configured to complete tasks in accordance with alertprofile generation component 198 and alert profile management component201 to provide an alert resolution profile and to update the alertresolution profile. Additionally or alternatively, data generated by thediagnostic contextualization component 115 as well as data related tothe diagnostic bit set 236 and received by the diagnosticcontextualization component 115 is used to generate additional displayson the dashboard 375 based upon data related to the diagnostic bit set236, data related to the contextualized alert, data related to thegenerated alert resolution status, and data related to the alertresolution profile. In an embodiment, priority distribution display 408provides an alternative representation of data related to the alertresolution profile.

FIG. 7 is an exemplary screen shot depicting a user interface fordisplaying a list of contextualized alerts according to an embodiment ofthe present invention. The contextualized alerts are organized as aprioritized alert list 441 of asset-related details ordered by severity.In an embodiment, an alert display 444 is comprised of the alert list441, and the alert list 441 is comprised of contextualized alerts suchas contextualized severity ordered alert 453. Data accessed to renderthe prioritized alert list 441 and data accessed to render thefunctionalities provided by the alert display 444 are related to datathe service interface 124 accesses in the asset repository 109 whengenerating the event-based data set 230. The alert list 441 is furthercomprised of data configured to allow the list to be organized intocontextualized categories 447. The contextualized categories 447comprise, for example, tag id data, alert message data, time stamp data,NAMUR category data, alert type data, asset type data, manufacturerdata, and the like. Acknowledgement indications 450 allow forindications to be entered with respect to the alert list 441. In anembodiment, the acknowledgement indications 450 allow for indications tobe entered with respect to the acknowledgement or rejection of acontextualized alert 453.

FIG. 8 is an exemplary screen shot of a user interface for displayingdetailed alert data related to received event data, according to anembodiment of the present invention. In the illustrated embodiment, datagenerated by the diagnostic contextualization component 115 as well asdata related to the diagnostic bit set 236 and received by thediagnostic contextualization component 115 is used to generate the dataused in the contextualized alert detail display 486. The contextualizedalert detail display 486 is generated based on data related to acontextualized alert, such as contextualized alert 453 for example.Additionally or alternatively, contextualized alert detail display 486is generated based on data related to a summarized alert 387. In anembodiment, the contextualized alert detail display 486 is organizedaccording to alert detail data relating to alert identification tag 489data. In an embodiment, the contextualized detail display 486 comprisesalert tag detail display 492, alert history display 495, asset detaildisplay 498, and asset location display 501.

With further reference to FIG. 8, tag alert detail display 492 iscomprised of, for example, general area data, problem description data,type data, priority data, state data, time stamp data, and the like. Inan embodiment, data accessed to render the tag alert detail display 492and data accessed to render the functionalities provided by the tagalert detail display 492 are related to data the service interface 124accesses in the asset repository 109 when generating the event-baseddata set 230. Alert history display 495 is comprised of, for example,same type tag alert data within the last 24 hours, any type tag alertdata within the last 24 hours, any type tag alert data within the last30 days, and a “more history” button for receiving input relating to thedisplay of additional alert history. In yet another embodiment, assetdetails display 498 is comprised of manufacturer data, model data, assettype data, commission date data, firmware version data, and/or serialnumber data. It is to be understood that this is the type of informationcollected in the process of configuring asset 112. Aspects of thepresent invention permits constructing a historical record ofmaintenance-related data for a configuration-free asset 112 based on theasset identification record when an asset identification record is notavailable because the particular asset 112 had not been previouslyconfigured. In another embodiment, the asset location display 501 isgenerated based on location data corresponding to latitude and longitudecoordinates. Acknowledgement indications 450 are generated forcontextualized alert detail display 486, and are configured for allowingindications to be entered with respect to a contextualized alert 453.

Still referring to FIG. 8, the alert detail display 486 furthercomprises an alert profile request 503 indication configured toautomatically generate an alert profile in part based upon the datacomprising the contextualized alert details display 486. In anembodiment, upon receiving input related to the alert profile request503, the diagnostic contextualization component 115 is configured toexecute alert profile generation 198 and alert profile management 201 asdescribed herein. Receiving an indication related to alert profilegeneration 503 results in the creation of an alert resolution profileand receiving an indication related to the alert profile generationindication 503 results in providing a result related to actionableoutput to an alert resolution profile to update the alert resolutionprofile.

The Abstract and Summary are provided to help the reader quicklyascertain the nature of the technical disclosure. They are submittedwith the understanding that they will not be used to interpret or limitthe scope or meaning of the claims. The Summary is provided to introducea selection of concepts in simplified form that are further described inthe Detailed Description. The Summary is not intended to identify keyfeatures or essential features of the claimed subject matter, nor is itintended to be used as an aid in determining the claimed subject matter.

For purposes of illustration, programs and other executable programcomponents, such as the operating system, are illustrated herein asdiscrete blocks. It is recognized, however, that such programs andcomponents reside at various times in different storage components of acomputing device, and are executed by a data processor(s) of the device.

Although described in connection with an exemplary computing systemenvironment, embodiments of the aspects of the invention are operationalwith numerous other general purpose or special purpose computing systemenvironments or configurations. The computing system environment is notintended to suggest any limitation as to the scope of use orfunctionality of any aspect of the invention. Moreover, the computingsystem environment should not be interpreted as having any dependency orrequirement relating to any one or combination of components illustratedin the exemplary operating environment. Examples of well-known computingsystems, environments, and/or configurations that may be suitable foruse with aspects of the invention include, but are not limited to,personal computers, server computers, hand-held or laptop devices,multiprocessor systems, microprocessor-based systems, set top boxes,programmable consumer electronics, mobile telephones, network PCs,minicomputers, mainframe computers, distributed computing environmentsthat include any of the above systems or devices, and the like.

Embodiments of the aspects of the invention may be described in thegeneral context of data and/or processor-executable instructions, suchas program modules, stored one or more tangible, non-transitory storagemedia and executed by one or more processors or other devices.Generally, program modules include, but are not limited to, routines,programs, objects, components, and data structures that performparticular tasks or implement particular abstract data types. Aspects ofthe invention may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules may be located in both local and remotestorage media including memory storage devices.

In operation, processors, computers and/or servers may execute theprocessor-executable instructions (e.g., software, firmware, and/orhardware) such as those illustrated herein to implement aspects of theinvention.

Embodiments of the aspects of the invention may be implemented withprocessor-executable instructions. The processor-executable instructionsmay be organized into one or more processor-executable components ormodules on a tangible processor readable storage medium. Aspects of theinvention may be implemented with any number and organization of suchcomponents or modules. For example, aspects of the invention are notlimited to the specific processor-executable instructions or thespecific components or modules illustrated in the figures and describedherein. Other embodiments of the aspects of the invention may includedifferent processor-executable instructions or components having more orless functionality than illustrated and described herein.

The order of execution or performance of the operations in embodimentsof the aspects of the invention illustrated and described herein is notessential, unless otherwise specified. That is, the operations may beperformed in any order, unless otherwise specified, and embodiments ofthe aspects of the invention may include additional or fewer operationsthan those disclosed herein. For example, it is contemplated thatexecuting or performing a particular operation before, contemporaneouslywith, or after another operation is within the scope of aspects of theinvention.

When introducing elements of aspects of the invention or the embodimentsthereof, the articles “a,” “an,” “the,” and “said” are intended to meanthat there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

In view of the above, it will be seen that several advantages of theaspects of the invention are achieved and other advantageous resultsattained.

Not all of the depicted components illustrated or described may berequired. In addition, some implementations and embodiments may includeadditional components. Variations in the arrangement and type of thecomponents may be made without departing from the spirit or scope of theclaims as set forth herein. Additional, different or fewer componentsmay be provided and components may be combined. Alternatively or inaddition, a component may be implemented by several components.

The above description illustrates the aspects of the invention by way ofexample and not by way of limitation. This description enables oneskilled in the art to make and use the aspects of the invention, anddescribes several embodiments, adaptations, variations, alternatives anduses of the aspects of the invention, including what is presentlybelieved to be the best mode of carrying out the aspects of theinvention. Additionally, it is to be understood that the aspects of theinvention is not limited in its application to the details ofconstruction and the arrangement of components set forth in thefollowing description or illustrated in the drawings. The aspects of theinvention are capable of other embodiments and of being practiced orcarried out in various ways. Also, it will be understood that thephraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting.

Having described aspects of the invention in detail, it will be apparentthat modifications and variations are possible without departing fromthe scope of aspects of the invention as defined in the appended claims.It is contemplated that various changes could be made in the aboveconstructions, products, and process without departing from the scope ofaspects of the invention. In the preceding specification, variouspreferred embodiments have been described with reference to theaccompanying drawings. It will, however, be evident that variousmodifications and changes may be made thereto, and additionalembodiments may be implemented, without departing from the broader scopeof the aspects of the invention as set forth in the claims that follow.The specification and drawings are accordingly to be regarded in anillustrative rather than restrictive sense.

What is claimed is:
 1. A computer implemented asset monitoring systeminterfacing with a commissioning component, said computer implementedsystem comprising: an asset repository storing asset-related data, theasset-related data being related to one or more commissioned industrialprocess assets of an industrial process control system, theasset-related data stored in the asset repository comprising an assetmaintenance record corresponding to each of the commissioned industrialprocess assets; a diagnostic contextualization component coupled to theasset repository and configured to deploy configured parameters to oneor more non-commissioned industrial process assets having no previousasset configuration within the system for commissioning thenon-commissioned industrial process assets; and a service interfacecoupled to the asset repository and to a particular non-commissionedindustrial process asset of the industrial process control system;wherein the diagnostic contextualization component is further configuredfor: receiving, via the service interface, event data from theparticular non-commissioned industrial process asset, wherein the eventdata comprises an asset parameter descriptive of a condition of theparticular non-commissioned industrial process asset within theindustrial process control system, and wherein the particularnon-commissioned industrial process asset has no previous assetconfiguration within the asset monitoring system; accessing, via theservice interface, the asset-related data in the asset repositorycorresponding to the particular non-commissioned industrial processasset based upon the received event data; generating an event-based dataset based upon the accessed asset-related data; determining, based uponcomparing the accessed asset-related data in the asset repository to thereceived event data, whether an asset maintenance record correspondingto the particular non-commissioned industrial process asset exists inthe asset repository; in response to the determining, where the assetmaintenance record is determined to not exist in the asset repositoryindicating the particular non-commissioned industrial process asset hasnot been commissioned and has no previous asset configuration within thesystem, creating a new asset identification record corresponding to theparticular non-commissioned industrial process asset, the new assetidentification record comprising: the generated event-based data set,and additional asset-related data collected, via the service interface,from the particular non-commissioned industrial process asset, whereinthe additional asset-related data is collected based on assetidentification data identifying the particular non-commissionedindustrial process asset; rendering the new asset identification recordin the asset repository in a configuration consistent with the one ormore commissioned industrial process assets of the industrial processcontrol system; and deploying configured parameters to the particularnon-commissioned industrial process asset corresponding to the new assetidentification record such that the particular non-commissionedindustrial process asset corresponding to the new asset identificationrecord becomes commissioned within the industrial process control systemby the commissioning component.
 2. The computer implemented system ofclaim 1, wherein the diagnostic contextualization component is furtherconfigured to maintain a previously commissioned industrial processasset by combining the accessed asset-related data with the receivedevent data to update the asset maintenance record where the assetmaintenance record is determined to previously exist in the assetrepository.
 3. The computer implemented system of claim 1, wherein theservice interface comprises a WCF service interface and wherein theasset-related data further comprises data descriptive of the particularnon-commissioned industrial process asset.
 4. The computer implementedsystem of claim 1, wherein the asset parameter comprises a diagnosticbit set descriptive of a condition of the particular non-commissionedindustrial process asset.
 5. The computer implemented system of claim 1,wherein generating the event-based data set further comprises collectingadditional asset-related data from the service interface related to atleast one of: asset vendor data, model data, serial number data,location data, and version data.
 6. The computer implemented system ofclaim 1, wherein the event data comprises an alert descriptive of analert condition of the particular non-commissioned industrial processasset, and wherein the diagnostic contextualization component is furtherconfigured for combining the accessed asset-related data with the eventdata to generate an alert log entry in the asset maintenance record, thealert log entry comprising at least one of: data describing a mitigatedstate of the alert; data associating each asset with an active alertrelated to the asset; and data associating each asset with an alertresolution profile related to the asset.
 7. The system of claim 1,wherein the service interface further comprises a set of serviceinterfaces configured to parse at least one of the following from theasset-related data: implementation data related to implementing one ormore asset maintenance services natively on the asset; and data relatedto transforming the alert into a protocol-specific format.
 8. A tangibleprocessor-readable memory storing processor-executable instructionsthat, when executed by a processor, configure the processor to interfacewith a commissioning component and further configure the processor to:receive, via a service interface, event data from a non-commissionedindustrial process asset, wherein the event data comprises an assetparameter descriptive of a condition of the non-commissioned industrialprocess asset within an industrial process control system; collect, viathe service interface, asset-related data corresponding to thenon-commissioned industrial process asset from an asset repository basedupon the received event data; generate an event-based data set basedupon the collected asset-related data; determine, based upon comparingthe collected asset-related data to the received event data, whether anasset maintenance record corresponding to the non-commissionedindustrial process asset exists in the asset repository; when the assetmaintenance record is determined to not exist in the asset repositoryindicating the non-commissioned industrial process asset has not beencommission and has no previous asset configuration within the system,create a new asset identification record corresponding to thenon-commissioned industrial process asset, the new asset identificationrecord comprising: the generated event-based data set, and additionalasset-related data collected, via the service interface, from thenon-commissioned industrial process asset, wherein the additionalasset-related data is collected based on asset identification dataidentifying the non-commissioned industrial process asset; render thenew asset identification record in an asset repository in aconfiguration consistent with one or more commissioned industrialprocess assets of the industrial process control system; and deployconfigured parameters to the non-commissioned industrial process assetcorresponding to the new asset identification record such that thenon-commissioned industrial process asset corresponding to the new assetidentification record becomes commissioned within the industrial processcontrol system by the commissioning component.
 9. The tangibleprocessor-readable memory of claim 8, the instructions furthercomprising instructions that, when executed by the processor, configurethe processor to: receive event data from a commissioned industrialprocess asset; collect, via the service interface, asset-related datacorresponding to the commissioned industrial process asset from theasset repository based upon the received event data; determine, basedupon comparing the collected asset-related data corresponding to thecommissioned industrial process asset to the asset identificationrecords in the asset repository, that the asset maintenance recordcorresponding to the commissioned industrial process asset exists in theasset repository; and combine the collected asset-related datacorresponding to the commissioned industrial process asset with thereceived event data from the commissioned industrial process asset toupdate the asset maintenance record for the commissioned industrialprocess asset where the asset maintenance record is determined topreviously exist in the asset repository.
 10. The tangibleprocessor-readable memory of claim 8, wherein the service interfacecomprises a WCF service interface and wherein the asset-related datafurther comprises data descriptive of the asset.
 11. The tangibleprocessor-readable memory of claim 8, wherein the asset parametercomprises a diagnostic bit set descriptive of a condition of thenon-commissioned industrial process asset.
 12. The tangibleprocessor-readable memory of claim 8, wherein the instructions that,when executed by the processor, configure the processor to generate theevent-based data set further configure the processor to collectadditional asset-related data from the service interface related to atleast one of: asset vendor data, model data, serial number data,location data, and version data.
 13. The tangible processor-readablememory of claim 8, wherein the event data comprises an alert descriptiveof industrial process asset, and the instructions further comprisinginstructions that, when executed by the processor, configure theprocessor to combine the asset-related data with the event data togenerate an alert log entry in the asset maintenance record, the alertlog entry comprising at least one of: data describing a mitigated stateof the alert; data associating each asset with an active alert relatedto the asset; and data associating each asset with an alert resolutionprofile related to the asset.
 14. The tangible processor-readable memoryof claim 8, wherein the service interface further comprises a set ofservice interfaces configured to parse at least one of the followingfrom the asset-related data: implementation data related to implementingone or more asset maintenance services natively on the asset; and datarelated to transforming the alert into a protocol-specific format.
 15. Acomputerized method for operating an asset monitoring system whichinterfaces with a commissioning component to generate and update assetmaintenance records for industrial process assets having no previousasset commission within the asset monitoring system, comprising:receiving, via a service interface, event data from a non-commissionedindustrial process asset, wherein the event data comprises an assetparameter descriptive of a condition of the non-commissioned industrialprocess asset within an industrial process control system; collecting,via the service interface, asset-related data corresponding to thenon-commissioned industrial process asset from an asset repository basedupon the received event data; generating an event-based data set basedupon the collected asset-related data; determining, based upon comparingthe collected asset-related data to the received event data, whether anasset maintenance record corresponding to the non-commissionedindustrial process asset exists in the asset repository; when the assetmaintenance record is determined to not exist in the asset repositoryindicating the non-commissioned industrial process asset has not beencommission and has no previous asset configuration within the system,creating a new asset identification record corresponding to thenon-commissioned industrial process asset, the new asset identificationrecord comprising: the generated event-based data set, and additionalasset-related data collected, via the service interface, from thenon-commissioned industrial process asset, wherein the additionalasset-related data is collected based on asset identification dataidentifying the non-commissioned industrial process asset; rendering thenew asset identification record in an asset repository in aconfiguration consistent with one or more commissioned industrialprocess assets of the industrial process control system; and deployingconfigured parameters to the non-commissioned industrial process assetcorresponding to the new asset identification record such that thenon-commissioned industrial process asset corresponding to the new assetidentification record becomes commissioned within the industrial processcontrol system by the commissioning component.
 16. The computerizedmethod of claim 15, further comprising: receiving event data from acommissioned industrial process asset; collecting, via the serviceinterface, asset-related data corresponding to the commissionedindustrial process asset from the asset repository based upon thereceived event data; determining, based upon comparing the collectedasset-related data corresponding to the commissioned industrial processasset to the asset identification records in the asset repository, thatthe asset maintenance record corresponding to the commissionedindustrial process asset exists in the asset repository; and combiningthe collected asset-related data corresponding to the commissionedindustrial process asset with the received event data from thecommissioned industrial process asset to update the asset maintenancerecord for the commissioned industrial process asset where the assetmaintenance record is determined to previously exist in the assetrepository.
 17. The computerized method of claim 15, wherein generatingthe event-based data set further comprises collecting additionalasset-related data from the service interface related to at least oneof: asset vendor data, model data, serial number data, location data,and version data.
 18. The computerized method of claim 15, wherein theevent data comprises an alert descriptive of the industrial processasset, and further comprising combining the asset-related data with theevent-based data set to generate an alert log entry in the assetmaintenance record, the alert log entry comprising at least one of: datadescribing a mitigated state of the alert; data associating each assetwith an active alert related to the asset; and data associating eachasset with an alert resolution profile related to the asset.
 19. Thecomputerized method of claim 15, wherein the service interface furthercomprises a set of service interfaces configured to parseprotocol-specific format information from the asset-related data. 20.The computerized method of claim 15, wherein the asset parametercomprises a diagnostic bit set descriptive of a condition of thenon-commissioned industrial process asset.